Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60d3bfce7b3b6ce475f8ef1e48115f58f80390bd7f6c540badd8154d3a311ea1

Tx prefix hash: 4cd05567e1f3a4deb841b3db4ebfdf8819b6a34cf267be93390230fef8cea45b
Tx public key: 5173d233878894c51af094f86b09454441cb73f1e08023ff738c93a45c43a571
Timestamp: 1578433049 Timestamp [UCT]: 2020-01-07 21:37:29 Age [y:d:h:m:s]: 04:315:21:31:53
Block: 40787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115090 RingCT/type: yes/0
Extra: 015173d233878894c51af094f86b09454441cb73f1e08023ff738c93a45c43a571021100000005d81c26c0000000000000000000

1 output(s) for total of 449.639109709000 dcy

stealth address amount amount idx
00: 219eee7a3eff13ba68e4e72d5798d07d57e5baae4044b6e20f7111a6ce689d8a 449.639109709000 71966 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": 40797, "vin": [ { "gen": { "height": 40787 } } ], "vout": [ { "amount": 449639109709, "target": { "key": "219eee7a3eff13ba68e4e72d5798d07d57e5baae4044b6e20f7111a6ce689d8a" } } ], "extra": [ 1, 81, 115, 210, 51, 135, 136, 148, 197, 26, 240, 148, 248, 107, 9, 69, 68, 65, 203, 115, 241, 224, 128, 35, 255, 115, 140, 147, 164, 92, 67, 165, 113, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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