Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2af4902a02d2e96d566792fe08bce88506953e07b7c8d524712afab54cf35208

Tx prefix hash: eec066390f6080d5242cecbcc0811a7f30b0bad3820101ed7758f85797df0966
Tx public key: 8aa4277b7164c16a726a6076853f38ab1b8882920ca1508e7eba9e5a6bd4fdc0
Timestamp: 1720793750 Timestamp [UCT]: 2024-07-12 14:15:50 Age [y:d:h:m:s]: 00:280:01:15:34
Block: 1064150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200085 RingCT/type: yes/0
Extra: 018aa4277b7164c16a726a6076853f38ab1b8882920ca1508e7eba9e5a6bd4fdc002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8048b5e59dcfb17fa3734e3b9ca1bf54611301232ac6d4c59a00b78d5f8e4b5 0.600000000000 1534673 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": 1064160, "vin": [ { "gen": { "height": 1064150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8048b5e59dcfb17fa3734e3b9ca1bf54611301232ac6d4c59a00b78d5f8e4b5" } } ], "extra": [ 1, 138, 164, 39, 123, 113, 100, 193, 106, 114, 106, 96, 118, 133, 63, 56, 171, 27, 136, 130, 146, 12, 161, 80, 142, 126, 186, 158, 90, 107, 212, 253, 192, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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