Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15fb297f053683b2575ab1b00980ffd2c3f5d4443dbc57d91a68583b520e507b

Tx prefix hash: 1a7303c03805293d653c0c04c67e4c1e0f2456f5e10d0513d0c198b42a1395cf
Tx public key: 7157c81c1ee43255e5e4069301ca31bdb4000c49bfef5d45aa2e373d24ee24e8
Timestamp: 1740366435 Timestamp [UCT]: 2025-02-24 03:07:15 Age [y:d:h:m:s]: 00:270:14:42:58
Block: 1225937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191167 RingCT/type: yes/0
Extra: 017157c81c1ee43255e5e4069301ca31bdb4000c49bfef5d45aa2e373d24ee24e8021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be4e61f4cb28464a6d33fbbcf173b98556aeb424f1d2c049186f2df6c19b692d 0.600000000000 1712808 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": 1225947, "vin": [ { "gen": { "height": 1225937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be4e61f4cb28464a6d33fbbcf173b98556aeb424f1d2c049186f2df6c19b692d" } } ], "extra": [ 1, 113, 87, 200, 28, 30, 228, 50, 85, 229, 228, 6, 147, 1, 202, 49, 189, 180, 0, 12, 73, 191, 239, 93, 69, 170, 46, 55, 61, 36, 238, 36, 232, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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