Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acc95ec444461b65d4b340f3d58b0fbcdac0a12edff14502d67fb19c602798a8

Tx prefix hash: d54ee257b08a9866ce956dbc11de2ca5f051b7447810e0b8651227c463594bff
Tx public key: b59c5ce8d664d4a73c1ec3a94d8380823014137cb5268da9f8a5e9f2f1934bcc
Timestamp: 1704733110 Timestamp [UCT]: 2024-01-08 16:58:30 Age [y:d:h:m:s]: 01:166:16:03:30
Block: 930973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380057 RingCT/type: yes/0
Extra: 01b59c5ce8d664d4a73c1ec3a94d8380823014137cb5268da9f8a5e9f2f1934bcc0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66b8bb1d4127bb986e7b86cd48022595d6d407ff8e55975bcaaa0aec19bbd68f 0.600000000000 1388865 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": 930983, "vin": [ { "gen": { "height": 930973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b8bb1d4127bb986e7b86cd48022595d6d407ff8e55975bcaaa0aec19bbd68f" } } ], "extra": [ 1, 181, 156, 92, 232, 214, 100, 212, 167, 60, 30, 195, 169, 77, 131, 128, 130, 48, 20, 19, 124, 181, 38, 141, 169, 248, 165, 233, 242, 241, 147, 75, 204, 2, 17, 0, 0, 0, 7, 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