Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcebc2f57eafd5d56dbae2d8bb7b260ffac011cb003489db87558eb54bb14c68

Tx prefix hash: 024ad4e23e844ac76a31255e1cbb8b913fdf02f3c8e3386d0a3b4d2fff9291d1
Tx public key: a6961aa1395a60739d4576fca13a2b670b95bfe50b9702206d09cd96a5cb57d7
Timestamp: 1735463826 Timestamp [UCT]: 2024-12-29 09:17:06 Age [y:d:h:m:s]: 00:172:02:52:53
Block: 1185620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122712 RingCT/type: yes/0
Extra: 01a6961aa1395a60739d4576fca13a2b670b95bfe50b9702206d09cd96a5cb57d70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 648185177417fa5a38c8d7ed5ada81453034a846a0a5a29281c1500ef57e49f3 0.600000000000 1672095 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": 1185630, "vin": [ { "gen": { "height": 1185620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "648185177417fa5a38c8d7ed5ada81453034a846a0a5a29281c1500ef57e49f3" } } ], "extra": [ 1, 166, 150, 26, 161, 57, 90, 96, 115, 157, 69, 118, 252, 161, 58, 43, 103, 11, 149, 191, 229, 11, 151, 2, 32, 109, 9, 205, 150, 165, 203, 87, 215, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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