Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd14974f9b3179e812fad3c4650aa88671af53e5ebed559532c7cb75160ceb4b

Tx prefix hash: e4ecdc994d676e3ef458b361639bb1297d575c23456656b84f49439e639afadc
Tx public key: 9808ea3383fafd0d194d94af41b7d0ec2e321f6a7743261c874101d3f95d612e
Timestamp: 1743595383 Timestamp [UCT]: 2025-04-02 12:03:03 Age [y:d:h:m:s]: 00:231:02:11:09
Block: 1252681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162890 RingCT/type: yes/0
Extra: 019808ea3383fafd0d194d94af41b7d0ec2e321f6a7743261c874101d3f95d612e0211000000104060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ce77a6a5118104b1c1d25dde1f309aaee420bd55bb7cc52a722d8dd41bf9dce 0.600000000000 1739762 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": 1252691, "vin": [ { "gen": { "height": 1252681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ce77a6a5118104b1c1d25dde1f309aaee420bd55bb7cc52a722d8dd41bf9dce" } } ], "extra": [ 1, 152, 8, 234, 51, 131, 250, 253, 13, 25, 77, 148, 175, 65, 183, 208, 236, 46, 50, 31, 106, 119, 67, 38, 28, 135, 65, 1, 211, 249, 93, 97, 46, 2, 17, 0, 0, 0, 16, 64, 96, 246, 210, 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