Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 744008f3d75ed22922a2170b2b7ae0c370f589b6ffc7a7a4d7013b2cfb143173

Tx prefix hash: 8d7d61a194e77d1bc5705f73a613448db6822908d90719bff8873d6288128a95
Tx public key: fbb2b2e9d2c4e4f94ffc0964f29aebf8a1d6b2a9f7a48a0f01488ee05d74e7ad
Timestamp: 1717343577 Timestamp [UCT]: 2024-06-02 15:52:57 Age [y:d:h:m:s]: 01:162:17:22:16
Block: 1035544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374866 RingCT/type: yes/0
Extra: 01fbb2b2e9d2c4e4f94ffc0964f29aebf8a1d6b2a9f7a48a0f01488ee05d74e7ad02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c552f596b3006de9f38fdf67eaf0ead0614f5b449dffffa81c1144137306dc3 0.600000000000 1504065 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": 1035554, "vin": [ { "gen": { "height": 1035544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c552f596b3006de9f38fdf67eaf0ead0614f5b449dffffa81c1144137306dc3" } } ], "extra": [ 1, 251, 178, 178, 233, 210, 196, 228, 249, 79, 252, 9, 100, 242, 154, 235, 248, 161, 214, 178, 169, 247, 164, 138, 15, 1, 72, 142, 224, 93, 116, 231, 173, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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