Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd0c46b93e0a796662d4640385e15d49a5ab9738527662754f9c57d2efac3dc9

Tx prefix hash: ce2b09ad116edb26972a005a00c9a0fe085af3fa02668348e2858d685b641d5d
Tx public key: 71c1d6063e8385aa8de1013e85c8431e2afab308d6e63f4dc5162a74dfdacf03
Timestamp: 1737190610 Timestamp [UCT]: 2025-01-18 08:56:50 Age [y:d:h:m:s]: 00:151:01:27:55
Block: 1199925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107663 RingCT/type: yes/0
Extra: 0171c1d6063e8385aa8de1013e85c8431e2afab308d6e63f4dc5162a74dfdacf03021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9acf5fa38824a34c5bf07d2e1e63618512f3227381b5c722601542cbdebca84 0.600000000000 1686564 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": 1199935, "vin": [ { "gen": { "height": 1199925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9acf5fa38824a34c5bf07d2e1e63618512f3227381b5c722601542cbdebca84" } } ], "extra": [ 1, 113, 193, 214, 6, 62, 131, 133, 170, 141, 225, 1, 62, 133, 200, 67, 30, 42, 250, 179, 8, 214, 230, 63, 77, 197, 22, 42, 116, 223, 218, 207, 3, 2, 17, 0, 0, 0, 5, 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