Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3ebe4a18c8ed71095c318cdf0a1ee8e2f3492089ffba6bb1f79cd5e079e2633

Tx prefix hash: 46eb8b100ec2ad95b98158c30fc02f52087d8b4a6c750259436ea7c12d6c2fd0
Tx public key: c681b16656c74c671fc38d86b7fc6ef535700e22686f1dc7b27a7b8d67cfee94
Timestamp: 1696974009 Timestamp [UCT]: 2023-10-10 21:40:09 Age [y:d:h:m:s]: 01:102:00:18:10
Block: 866869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334120 RingCT/type: yes/0
Extra: 01c681b16656c74c671fc38d86b7fc6ef535700e22686f1dc7b27a7b8d67cfee94021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.823575048000 dcy

stealth address amount amount idx
00: 2153fb9b95cb62fa28fc2534dfc5bf787086fcb0e166abb8bb4da4ddc9c2872c 0.823575048000 1321507 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": 866879, "vin": [ { "gen": { "height": 866869 } } ], "vout": [ { "amount": 823575048, "target": { "key": "2153fb9b95cb62fa28fc2534dfc5bf787086fcb0e166abb8bb4da4ddc9c2872c" } } ], "extra": [ 1, 198, 129, 177, 102, 86, 199, 76, 103, 31, 195, 141, 134, 183, 252, 110, 245, 53, 112, 14, 34, 104, 111, 29, 199, 178, 122, 123, 141, 103, 207, 238, 148, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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