Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f71ed2e463fd370877c3e420d58212cc5b0e5a7ef78bcd0159a5867710ed7085

Tx prefix hash: bbf01818817c64b6986882fbd495626b749a5ff4866dcd329dc0c1ef9bd84681
Tx public key: a7b6dbf4d614d755c682d54a8a1be2c45408b7c0dc8c5e8ceb4303c8ef5987bc
Timestamp: 1699382689 Timestamp [UCT]: 2023-11-07 18:44:49 Age [y:d:h:m:s]: 01:130:23:30:46
Block: 886635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354809 RingCT/type: yes/0
Extra: 01a7b6dbf4d614d755c682d54a8a1be2c45408b7c0dc8c5e8ceb4303c8ef5987bc0211000000074b8f5122000000000000000000

1 output(s) for total of 0.708288496000 dcy

stealth address amount amount idx
00: 91e57da22a5280e8ac6b8e59f3eb61a0ed26bd2975ea74e2f2adb7420f4e8600 0.708288496000 1342464 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": 886645, "vin": [ { "gen": { "height": 886635 } } ], "vout": [ { "amount": 708288496, "target": { "key": "91e57da22a5280e8ac6b8e59f3eb61a0ed26bd2975ea74e2f2adb7420f4e8600" } } ], "extra": [ 1, 167, 182, 219, 244, 214, 20, 215, 85, 198, 130, 213, 74, 138, 27, 226, 196, 84, 8, 183, 192, 220, 140, 94, 140, 235, 67, 3, 200, 239, 89, 135, 188, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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