Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69e35bf670ad8837d1612b7fd941efc47dd8a1f3b7739239d791d271b2c9d69d

Tx prefix hash: 0c1058c97ebdb050c758cbcded2e4ce72e81da3e7361cd15267ae04af673ebea
Tx public key: 248da14070d8c5b016083c2d6eb9cea05e64ed0bb2728353c8cde5a95235a884
Timestamp: 1693909770 Timestamp [UCT]: 2023-09-05 10:29:30 Age [y:d:h:m:s]: 01:071:13:31:42
Block: 841428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312449 RingCT/type: yes/0
Extra: 01248da14070d8c5b016083c2d6eb9cea05e64ed0bb2728353c8cde5a95235a88402110000000475e3f0e9000000000000000000

1 output(s) for total of 0.999999567000 dcy

stealth address amount amount idx
00: a00de08872a7fdb11eb08e2cbc154801dd52956b244255a0af5dfd5e41204091 0.999999567000 1294458 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": 841438, "vin": [ { "gen": { "height": 841428 } } ], "vout": [ { "amount": 999999567, "target": { "key": "a00de08872a7fdb11eb08e2cbc154801dd52956b244255a0af5dfd5e41204091" } } ], "extra": [ 1, 36, 141, 161, 64, 112, 216, 197, 176, 22, 8, 60, 45, 110, 185, 206, 160, 94, 100, 237, 11, 178, 114, 131, 83, 200, 205, 229, 169, 82, 53, 168, 132, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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