Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 529332418d658f75409cd70abd9514a73445e6fc448d2ef5b5210aa877c98a76

Tx prefix hash: 5845bb070c7eb46e12cfd7b3bbda3863e7a3eb7c509e59eab9128182a7bafc80
Tx public key: 514faecd8d08a3e86f0e9351853bb5f29ff0b73463c431bfb3cf8de658fa51bc
Timestamp: 1704257057 Timestamp [UCT]: 2024-01-03 04:44:17 Age [y:d:h:m:s]: 01:014:12:00:41
Block: 927024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271704 RingCT/type: yes/0
Extra: 01514faecd8d08a3e86f0e9351853bb5f29ff0b73463c431bfb3cf8de658fa51bc02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d49a16ce0b82ded6e02097eec08a2c9f4e1aa5f7e4ffac61d1f9dcd1baebf02a 0.600000000000 1384824 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": 927034, "vin": [ { "gen": { "height": 927024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d49a16ce0b82ded6e02097eec08a2c9f4e1aa5f7e4ffac61d1f9dcd1baebf02a" } } ], "extra": [ 1, 81, 79, 174, 205, 141, 8, 163, 232, 111, 14, 147, 81, 133, 59, 181, 242, 159, 240, 183, 52, 99, 196, 49, 191, 179, 207, 141, 230, 88, 250, 81, 188, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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