Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7b4bd8f9298cb19467bd1122f147c678b2bbba3c626cd1c69ab52b55fd3de27

Tx prefix hash: f49976791ce87ed354d36248f53492ed3053d81593471f3dd3ca9c210f5ede7a
Tx public key: b30b45f83d1dc262fc30d95ac85a2fe2297d3ef2b57b59fd191e4f8ee8feed84
Timestamp: 1702420902 Timestamp [UCT]: 2023-12-12 22:41:42 Age [y:d:h:m:s]: 01:155:02:56:54
Block: 911837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371997 RingCT/type: yes/0
Extra: 01b30b45f83d1dc262fc30d95ac85a2fe2297d3ef2b57b59fd191e4f8ee8feed84021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cec308bbd3e3af6931575af135b60860fd22c54a182c21d062ee06b465f3b155 0.600000000000 1369053 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": 911847, "vin": [ { "gen": { "height": 911837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cec308bbd3e3af6931575af135b60860fd22c54a182c21d062ee06b465f3b155" } } ], "extra": [ 1, 179, 11, 69, 248, 61, 29, 194, 98, 252, 48, 217, 90, 200, 90, 47, 226, 41, 125, 62, 242, 181, 123, 89, 253, 25, 30, 79, 142, 232, 254, 237, 132, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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