Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7cde5726808a681fb8b695994f85da0669bc9eec14386a3ee3ddc78fdfe5b75

Tx prefix hash: b015dcfd877f51c27b9eb6fc8db152a6a26cb92a77a93c5baf1a4dcefb6b0585
Tx public key: 9016d750b96f1b11178a4ff842b547c64fb094cff5065acdd15b6f4ea4e2be5b
Timestamp: 1736919893 Timestamp [UCT]: 2025-01-15 05:44:53 Age [y:d:h:m:s]: 00:303:03:05:37
Block: 1197688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214148 RingCT/type: yes/0
Extra: 019016d750b96f1b11178a4ff842b547c64fb094cff5065acdd15b6f4ea4e2be5b02110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fe2914a4a2ef0e50efc5fb74c08721afe076b0f2ea8547f3c664cb34a15ce8e 0.600000000000 1684301 of 15

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": 1197698, "vin": [ { "gen": { "height": 1197688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fe2914a4a2ef0e50efc5fb74c08721afe076b0f2ea8547f3c664cb34a15ce8e" } } ], "extra": [ 1, 144, 22, 215, 80, 185, 111, 27, 17, 23, 138, 79, 248, 66, 181, 71, 198, 79, 176, 148, 207, 245, 6, 90, 205, 209, 91, 111, 78, 164, 226, 190, 91, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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