Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 544462123a53d5d3b3670c21685155d8ba023b9093284bf4515feee5a04a862c

Tx prefix hash: 51f7851fb8a85f5777e3c5ca8181fad1d03f35f51070e48787a60c259f0477d1
Tx public key: 6d3f8813abfde8cfc4f13de9ec910e6ce58cac65416ce2a3975b2c28913336ea
Timestamp: 1577766457 Timestamp [UCT]: 2019-12-31 04:27:37 Age [y:d:h:m:s]: 05:110:05:46:42
Block: 35465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1228609 RingCT/type: yes/0
Extra: 016d3f8813abfde8cfc4f13de9ec910e6ce58cac65416ce2a3975b2c28913336ea0211000000104ac5aa02000000000000000000

1 output(s) for total of 468.263802065000 dcy

stealth address amount amount idx
00: bdf99f8268027cb1e784d23b8ec50c1b178c20f77ff7c10fd6f1a9b9b7b7873e 468.263802065000 59827 of 0

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": 35475, "vin": [ { "gen": { "height": 35465 } } ], "vout": [ { "amount": 468263802065, "target": { "key": "bdf99f8268027cb1e784d23b8ec50c1b178c20f77ff7c10fd6f1a9b9b7b7873e" } } ], "extra": [ 1, 109, 63, 136, 19, 171, 253, 232, 207, 196, 241, 61, 233, 236, 145, 14, 108, 229, 140, 172, 101, 65, 108, 226, 163, 151, 91, 44, 40, 145, 51, 54, 234, 2, 17, 0, 0, 0, 16, 74, 197, 170, 2, 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