Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f903eb50cb1849e368f28f25ae2e761682e1418339c35de54e45662858947cd8

Tx prefix hash: f7bc8a0d1add4095e777a75a2bce906d87ef5baa5bc9dd51ab15a4cbfaf357fc
Tx public key: cafb362ab55a2048a87604561eab83931aea4ce7db87b3c7eebfcc6b726148d7
Timestamp: 1725934465 Timestamp [UCT]: 2024-09-10 02:14:25 Age [y:d:h:m:s]: 00:121:02:52:31
Block: 1106759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86613 RingCT/type: yes/0
Extra: 01cafb362ab55a2048a87604561eab83931aea4ce7db87b3c7eebfcc6b726148d7021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d379c2bdf13e66f1208bf19fbc4b74d8db08f1b48a7eb483789c7f76c571760e 0.600000000000 1584360 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": 1106769, "vin": [ { "gen": { "height": 1106759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d379c2bdf13e66f1208bf19fbc4b74d8db08f1b48a7eb483789c7f76c571760e" } } ], "extra": [ 1, 202, 251, 54, 42, 181, 90, 32, 72, 168, 118, 4, 86, 30, 171, 131, 147, 26, 234, 76, 231, 219, 135, 179, 199, 238, 191, 204, 107, 114, 97, 72, 215, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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