Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc437c40e839073e0ba4f52ce4590a92e9177818f30819bd8dc2ba254ca4f8b5

Tx prefix hash: fcb7c43e7aa5126e70e83574698e58655ee24cb2c55baf81c0330095dff5d15b
Tx public key: f2cfea7b23bfd1b952ecf91516db2095c1d6820e16b5133300c985d34529a2b4
Timestamp: 1695437574 Timestamp [UCT]: 2023-09-23 02:52:54 Age [y:d:h:m:s]: 01:127:03:30:08
Block: 854117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351937 RingCT/type: yes/0
Extra: 01f2cfea7b23bfd1b952ecf91516db2095c1d6820e16b5133300c985d34529a2b4021100000004faf35c9c000000000000000000

1 output(s) for total of 0.907728286000 dcy

stealth address amount amount idx
00: 5fa12e4aaae98865fd7bf353d27022d13e3dd3c52a1b9591fe0fac5054a245f4 0.907728286000 1308071 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": 854127, "vin": [ { "gen": { "height": 854117 } } ], "vout": [ { "amount": 907728286, "target": { "key": "5fa12e4aaae98865fd7bf353d27022d13e3dd3c52a1b9591fe0fac5054a245f4" } } ], "extra": [ 1, 242, 207, 234, 123, 35, 191, 209, 185, 82, 236, 249, 21, 22, 219, 32, 149, 193, 214, 130, 14, 22, 181, 19, 51, 0, 201, 133, 211, 69, 41, 162, 180, 2, 17, 0, 0, 0, 4, 250, 243, 92, 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