Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3bee40a8584ed438005d7ac13f16ffc1e58e4f2d6c40f889f730c4dc732f2c1

Tx prefix hash: bc2b43dc259cd56a073d5e03f35964c1037bb99d36d347ed5cfafdb9a613e066
Tx public key: 37ae18832781c2b6e275ca5b278b3315f3c6f2bc706b681534ef03c08d340478
Timestamp: 1672065659 Timestamp [UCT]: 2022-12-26 14:40:59 Age [y:d:h:m:s]: 02:048:05:56:40
Block: 661044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556137 RingCT/type: yes/0
Extra: 0137ae18832781c2b6e275ca5b278b3315f3c6f2bc706b681534ef03c08d340478021100000001e7ace25d000000000000000000

1 output(s) for total of 3.959923408000 dcy

stealth address amount amount idx
00: 67a38fa3d4ce19ae3042a10a9d015e87adb9dc9a8e250c97ec16d3062bc13c1e 3.959923408000 1101793 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": 661054, "vin": [ { "gen": { "height": 661044 } } ], "vout": [ { "amount": 3959923408, "target": { "key": "67a38fa3d4ce19ae3042a10a9d015e87adb9dc9a8e250c97ec16d3062bc13c1e" } } ], "extra": [ 1, 55, 174, 24, 131, 39, 129, 194, 182, 226, 117, 202, 91, 39, 139, 51, 21, 243, 198, 242, 188, 112, 107, 104, 21, 52, 239, 3, 192, 141, 52, 4, 120, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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