Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4691d41059bfb65b918eac48866445807ce627d8e65f4062ca7f2b40ac8efc08

Tx prefix hash: 818120998c46315513b1397b2f575681176688f9d6b5764d7810c316451d472c
Tx public key: 490d938e9e38c2b1c363abf3ead724f810b7fb9d8239e2d9e4d10f7d4071e047
Timestamp: 1722780751 Timestamp [UCT]: 2024-08-04 14:12:31 Age [y:d:h:m:s]: 00:172:00:27:39
Block: 1080600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123037 RingCT/type: yes/0
Extra: 01490d938e9e38c2b1c363abf3ead724f810b7fb9d8239e2d9e4d10f7d4071e04702110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05b7f279cce25e0fad7c78a0b9e1adaa4de9608ab228e30bb17a8df8979a5f2d 0.600000000000 1554031 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": 1080610, "vin": [ { "gen": { "height": 1080600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05b7f279cce25e0fad7c78a0b9e1adaa4de9608ab228e30bb17a8df8979a5f2d" } } ], "extra": [ 1, 73, 13, 147, 142, 158, 56, 194, 177, 195, 99, 171, 243, 234, 215, 36, 248, 16, 183, 251, 157, 130, 57, 226, 217, 228, 209, 15, 125, 64, 113, 224, 71, 2, 17, 0, 0, 0, 7, 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