Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 731a5df13ddb75cd489c66687e314a5041c481990bd517776d2cf9aca68ef73d

Tx prefix hash: c569bfb1c9c9a6c983fe81923f82e40ae260ca4de60996183f109ded3b402160
Tx public key: fe9df0405376862c61cf49ff7a4ab786e818f6b62128b183e8a850c93435a7eb
Timestamp: 1696734063 Timestamp [UCT]: 2023-10-08 03:01:03 Age [y:d:h:m:s]: 01:193:14:57:19
Block: 864878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399427 RingCT/type: yes/0
Extra: 01fe9df0405376862c61cf49ff7a4ab786e818f6b62128b183e8a850c93435a7eb02110000000733af99f4000000000000000000

1 output(s) for total of 0.836180803000 dcy

stealth address amount amount idx
00: 84e34eb7d010e622a4032dd95c05de962efee0b0b8352b2bb92fcb3b18bee9a3 0.836180803000 1319400 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": 864888, "vin": [ { "gen": { "height": 864878 } } ], "vout": [ { "amount": 836180803, "target": { "key": "84e34eb7d010e622a4032dd95c05de962efee0b0b8352b2bb92fcb3b18bee9a3" } } ], "extra": [ 1, 254, 157, 240, 64, 83, 118, 134, 44, 97, 207, 73, 255, 122, 74, 183, 134, 232, 24, 246, 182, 33, 40, 177, 131, 232, 168, 80, 201, 52, 53, 167, 235, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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