Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 684da21b83583f7a2d5fd4793b7ae74e2279b7bc9c26b927d6a2bbe661f26c0d

Tx prefix hash: c3c011c7c864412a2f0cae79ae7b8bb0f3d5c7a5ec0a1a3c888b4f9624bcdcec
Tx public key: 85a8c34ecc8adf712dc4a71e7e727af5bc418e36773d05b385e3f6aeadce8ef2
Timestamp: 1715283357 Timestamp [UCT]: 2024-05-09 19:35:57 Age [y:d:h:m:s]: 00:248:12:09:01
Block: 1018456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177866 RingCT/type: yes/0
Extra: 0185a8c34ecc8adf712dc4a71e7e727af5bc418e36773d05b385e3f6aeadce8ef20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0253ada6b9aac1cded449a56332081b41ff3c731468d80e4f39109d9d8fa4571 0.600000000000 1482245 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": 1018466, "vin": [ { "gen": { "height": 1018456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0253ada6b9aac1cded449a56332081b41ff3c731468d80e4f39109d9d8fa4571" } } ], "extra": [ 1, 133, 168, 195, 78, 204, 138, 223, 113, 45, 196, 167, 30, 126, 114, 122, 245, 188, 65, 142, 54, 119, 61, 5, 179, 133, 227, 246, 174, 173, 206, 142, 242, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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