Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4e6a1745db629c2f22c6b505b22d870e4bd8ebd525d4149595c90d9469ce202b

Tx prefix hash: d7ab68f64df2a0c169ccd2a3dba116bf7e3b81467b726d4dff8e8cb372d8289b
Tx public key: 557ae791664591cc60a771f5d29c9f323e909ec300f3837712c71ea9a978552d
Timestamp: 1735764494 Timestamp [UCT]: 2025-01-01 20:48:14 Age [y:d:h:m:s]: 00:170:01:47:07
Block: 1188114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121225 RingCT/type: yes/0
Extra: 01557ae791664591cc60a771f5d29c9f323e909ec300f3837712c71ea9a978552d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44496f2250444a45c6cb9db065c9639f855bde4edb5836a391beb59ae5eadf77 0.600000000000 1674613 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1188124, "vin": [ { "gen": { "height": 1188114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44496f2250444a45c6cb9db065c9639f855bde4edb5836a391beb59ae5eadf77" } } ], "extra": [ 1, 85, 122, 231, 145, 102, 69, 145, 204, 96, 167, 113, 245, 210, 156, 159, 50, 62, 144, 158, 195, 0, 243, 131, 119, 18, 199, 30, 169, 169, 120, 85, 45, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8